home *** CD-ROM | disk | FTP | other *** search
- Path: portal.gmu.edu!rscernix!danpop
- From: danpop@mail.cern.ch (Dan Pop)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 11 Apr 96 10:30:12 GMT
- Organization: CERN European Lab for Particle Physics
- Message-ID: <danpop.829218612@rscernix>
- References: <dewar.828846122@schonberg> <828903511snz@genesis.demon.co.uk> <4kgjrc$4d@news.nyu.edu>
- NNTP-Posting-Host: ues5.cern.ch
- Mime-Version: 1.0
- Content-Type: text/plain; charset=US-ASCII
- Content-Transfer-Encoding: 7bit
- X-Newsreader: NN version 6.5.0 #7 (NOV)
-
- In <4kgjrc$4d@news.nyu.edu> halvin@acf4.nyu.edu (halvin) writes:
-
- >this might be slightly off-topic, but isn't there a difference between the
- >ANSI and POSIX versions of fprintf? if i remember correctly, the ANSI version
- >returns 0 on success and EOF on failure -- but the POSIX version returns the
- >number of characters printed, or a negative number to indicate failure.
-
- This is what you get for relying on your (faulty) memory when dealing
- with standards issues. From the ANSI C standard:
-
- The fprintf function returns the number of characters transmitted,
- or a negative value if an output error occurred.
-
- Dan
- --
- Dan Pop
- CERN, CN Division
- Email: danpop@mail.cern.ch
- Mail: CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland
-